When an OPC Studio product establishes a connection to an OPC UA server, it tries to do so in most effective manner. When necessary, it first calls the GetEndpoints service of the target OPC UA server, and preselects the endpoint. In other cases, the call to GetEndpoints can be skipped, and the endpoint is synthetised by OPC Studio components.

The endpoint demands preselection if at least of one the conditions below is fulfilled:

•    
• The AllowedMessageSecurityModes Property in the effective endpoint policy does not specify a precise (single) message security mode.
• The SecurityPolicyUriString Property is empty (i.e. does not specify a precise security policy URI).
• There is more than one configured user identity token in the UserIdentity Property.
• The AllowedMessageSecurityModes is not equal to SecurityNone, or the SecurityPolicyUriString is not equal to None ("http://opcfoundation.org/UA/SecurityPolicy#None"), and at the same time, the server certificate is not given in the ServerCertificate Property (or ServerCertificateByteArray Property) of the UAEndpointDescriptor.

This might seem quite complicated, but it boils down to a simple rule: If a product based on OPC Studio has information available that is precise enough to allow connection without calling GetEndpoints first, it will connect straight away. Otherwise, it will call GetEndpoints in order to obtain the list of available endpoints and select from them (= endpoint preselection).

In addition, the endpoint will be preselected if you set the AlwaysPreselectEndpoint Property to true.

Preselected Endpoints

Endpoint preselection is performed by calling the OPC UA GetEndpoints service on the target server, and applying the effective endpoint selection policy to it. The OPC UA server must therefore properly support the GetEndpoints service for endpoint preselection to work. When applying the endpoint selection policy yields an endpoint, the parameters of it are then used to create the OPC UA secure channel.

Synthetised Endpoints

Synthetised endpoints do not require use of the OPC UA GetEndpoints service as part of the connection process. They are therefore a bit faster to connect, and (more importantly) allow connections even to servers that do not support the GetEndpoints service (or do not support it properly). The client code in OPC Studio products simply uses the parameters from the effective endpoint selection policy when creating the OPC UA secure channel. The effective endpoint selection policy is then applied to the endpoints returned by the OPC UA server from the CreateSession service, and OPC Data Client checks whether the endpoint specified by the policy is available.

In most cases, for the synthetised endpoint to work, you will need to specify the user token policy Id, in the UserTokenPolicyId Property. The user token policy Ids are server-specific (for example, servers based on OPC Foundation OPC UA .NET stack use a string form of integers, starting from "0" upwards).